-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print all requests to console in debug mode #4365
Conversation
Good idea! |
Changed the approach to log on all requests, and print out the url's relative path. For example, output looks like:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, might steal this for the FC API client!
Just curious, can users do anything with these request IDs that might help them debug an error? Or is this ID just something we can use internally to debug?
I believe uses can log into their dashboard and access request logs based on requestID, but the idea is if they open an issue w/ us and include requests, we'd have more info on figuring out what's going on. |
Summary
It's kind of difficult to see when requests are failing. I propose we print requestID to the console so that it's easier to see/debug.
Motivation
Difficult to view requestId's unless you have a ton of breakpoints in code.
Testing
Manual testing.
Changelog